-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
made the default status of addons false #15722
Conversation
|
Welcome @swastik959! |
Hi @swastik959. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: swastik959 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Can one of the admins verify this patch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't want the the storage provisioner addons to be disabled by default, we just want them to show as correctly disabled when minikube profile list
is ran when they are in fact disabled.
@spowelljr can you please let me know where to look for this problem |
@shubhbapna is assigned the issue #15710, if they don't have any activity on the issue by the end of this week then we can unassign the issue and you can take it. |
@spowelljr sorry for the delay. I have opened a PR: |
minikube addons list
outputs wrong state for default addons #157103.I simply changed the default status of the sevices as false